.github/workflows/repo-maintenance.yml

Have you thought about adopting this? It's fine with me, I just want to make sure this is not slipping in unnoticed.

add webapp

Is there a particular reason why you do this? I maintain that no build output shall be part of the repo. The commit adds two new files yarn.lock in the repo root and node_modules/.yarn-integrity. I think you accidentally executed yarn in the repo root rather than in subfolder webapp? These two files should be cleaned up.

So in total, I'd like to propose merging ff44267 into master development and drop "add webapp" 😉

.github/workflows/repo-maintenance.yml

Guess it's fine. Would help to do our housekeeping.

I think you accidentally executed yarn in the repo root rather than in subfolder webapp? These two files should be cleaned up.

upps. You are right.

So in total, I'd like to propose merging ff44267 into master development and drop "add webapp" 😉

That's fine for me

As discussed, I moved the branch tip of this PR to ff44267, which effectively removes the commit I wasn't happy about.

FYI: I pushed tag v24.3.31 to this repo, pointing to the original upstream commit 1258865.

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.